Systems and methods for deriving platform feedback data for dynamic retrieval by downstream subsystems

ABSTRACT

Disclosed are methods, systems, and non-transitory computer-readable medium for deriving platform feedback data from raw feedback data for dynamic retrieval by downstream subsystems. For example, a method may include detecting a return notification trigger of a user, identifying segment data, determining a return notification form identifier based on the segment data, loading an electronic return notification form corresponding to the return notification form identifier, receiving raw feedback data from the user device, deriving platform feedback data from the raw feedback data using a plurality of mappings stored in one or more electronic mapping databases, and storing the platform feedback data in at least one of a feedback service component and a return notification service component, in one or more formats configured for retrieval by one or more downstream subsystems associated with managing and/or analyzing the one or more wearable items.

TECHNICAL FIELD

Various embodiments of the present disclosure generally relate to anelectronic platform for distribution of wearable items and, moreparticularly, storing user feedback data at a server system in such away that the feedback data may be effectively retrieved.

BACKGROUND

Online service provider systems may collect user feedback at anelectronic platform. Collecting user feedback data and electronicallyrendering the feedback data to other subsystems may help generate usefulanalytics data associated with user transactions, inventories, andoperations of the online service. However, there may be multipledifferent versions of electronic feedback forms to be utilized forcollecting user feedback data, depending on circumstances such astechnical contexts, users, or segments. For example, because some mobileapplication users may not update their applications to the latestversion in a certain time frame, the online service provider systems maybe running different versions of electronic feedback forms for userinterfaces of different users. In addition, different vendors orplatform tenants may, for example, require utilizing differentlyarranged electronic feedback forms to suit their own needs. Thus, it maybe highly desirable for an online service provider system to be able todynamically render different types of feedback forms onto different userinterfaces. It may also be highly desirable for an online serviceprovider system to be able to dynamically map the elements collectedfrom different electronic feedback forms to a uniform set of coremetrics that may be utilized by other subsystems of the online serviceprovider system.

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Unless otherwiseindicated herein, the materials described in this section are not priorart to the claims in this application and are not admitted to be priorart, or suggestions of the prior art, by inclusion in this section.

SUMMARY OF THE DISCLOSURE

According to certain aspects of the disclosure, systems and methods aredisclosed for deriving platform feedback data from user feedback dataassociated with online transactions.

In one embodiment, a computer-implemented method is disclosed forderiving platform feedback data from raw feedback data for dynamicretrieval by downstream subsystems. The computer-implemented method maycomprise: detecting, by one or more processors, a return notificationtrigger of a user for one or more wearable items physically shipped tothe user in response to one or more electronic transactions; in responseto detecting the return notification trigger, identifying, by the one ormore processors, segment data associated with at least one of the userand the one or more wearable items; determining, by the one or moreprocessors, a return notification form identifier based on the segmentdata, the return notification form identifier uniquely identifying anelectronic form to be filled out by the user; loading at one or moreuser interfaces of a user device of the user, by the one or moreprocessors, an electronic return notification form corresponding to thereturn notification form identifier; receiving, by the one or moreprocessors, via the electronic return notification form, raw feedbackdata from the user device; deriving, by the one or more processors,platform feedback data from the raw feedback data using a plurality ofmappings stored in one or more electronic mapping databases, wherein theplurality of mappings include one or more predefined mappings between afirst data set associated with the raw feedback data and a second dataset associated with the platform feedback data; and storing, by the oneor more processors, the platform feedback data in at least one of afeedback service component and a return notification service component,in one or more formats configured for retrieval by one or moredownstream subsystems associated with managing and/or analyzing the oneor more wearable items.

In accordance with another embodiment, a computer system is disclosedfor deriving platform feedback data from raw feedback data for dynamicretrieval by downstream subsystems. The computer system may comprise: amemory having processor-readable instructions stored therein; and atleast one processor configured to access the memory and execute theprocessor-readable instructions, which when executed by the processorconfigures the processor to perform a plurality of functions, includingfunctions for: detecting a return notification trigger of a user for oneor more wearable items physically shipped to the user in response to oneor more electronic transactions; in response to detecting the returnnotification trigger, identifying segment data associated with at leastone of the user and the one or more wearable items; determining a returnnotification form identifier based on the segment data, the returnnotification form identifier uniquely identifying an electronic form tobe filled out by the user; loading at one or more user interfaces of auser device of the user an electronic return notification formcorresponding to the return notification form identifier; receiving viathe electronic return notification form, raw feedback data from the userdevice; deriving platform feedback data from the raw feedback data usinga plurality of mappings stored in one or more electronic mappingdatabases, wherein the plurality of mappings include one or morepredefined mappings between a first data set associated with the rawfeedback data and a second data set associated with the platformfeedback data; and storing the platform feedback data in at least one ofa feedback service component and a return notification servicecomponent, in one or more formats configured for retrieval by one ormore downstream subsystems associated with managing and/or analyzing theone or more wearable items.

In accordance with another embodiment, a non-transitorycomputer-readable medium containing instructions is disclosed forderiving platform feedback data from raw feedback data for dynamicretrieval by downstream subsystems. The non-transitory computer-readablemedium may comprise instructions for: detecting a return notificationtrigger of a user for one or more wearable items physically shipped tothe user in response to one or more electronic transactions; in responseto detecting the return notification trigger, identifying segment dataassociated with at least one of the user and the one or more wearableitems; determining a return notification form identifier based on thesegment data, the return notification form identifier uniquelyidentifying an electronic form to be filled out by the user; loading atone or more user interfaces of a user device of the user an electronicreturn notification form corresponding to the return notification formidentifier; receiving via the electronic return notification form, rawfeedback data from the user device; deriving platform feedback data fromthe raw feedback data using a plurality of mappings stored in one ormore electronic mapping databases, wherein the plurality of mappingsinclude one or more predefined mappings between a first data setassociated with the raw feedback data and a second data set associatedwith the platform feedback data; and storing the platform feedback datain at least one of a feedback service component and a returnnotification service component, in one or more formats configured forretrieval by one or more downstream subsystems associated with managingand/or analyzing the one or more wearable items.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate various exemplary embodiments andtogether with the description, serve to explain the principles of thedisclosed embodiments.

FIG. 1 depicts an example environment in which methods, systems, andother aspects of the present disclosure may be implemented.

FIG. 2 depicts a schematic diagram showing an exemplary process forreceiving raw feedback data from a first type of user device andderiving platform feedback data at an integrated computing environment,according to one or more embodiments.

FIG. 3 depicts a schematic diagram showing an exemplary process forreceiving raw feedback data from a second type of user device andderiving platform feedback data at an integrated computing environment,according to one or more embodiments.

FIG. 4 depicts an exemplary method for deriving platform feedback datafrom raw feedback data for dynamic retrieval by downstream subsystems,according to one or more embodiments.

FIG. 5 depicts an exemplary computer device or system, in whichembodiments of the present disclosure, or portions thereof, may beimplemented.

DETAILED DESCRIPTION OF EMBODIMENTS

The following embodiments describe systems and methods for derivingplatform feedback data from user feedback data associated with onlinetransactions. When a server system of an online service provider detectsa trigger associated with a return notification (e.g., a notification ofa return of an item shipped to the user) from a user, the server systemmay prompt a user to input some feedback, such as, for example, theuser's experience with the item being returned. The received feedbackmay be used by other subsystems as relevant metrics or analytics for theonline service. The feedback may be received using an electronic formrendered at the user's device. However, different versions of electronicfeedback form may be rendered for different circumstances or user types.Thus, to transform a variety of raw feedback data into a set ofstandardized core metrics, the server system may generate and maintain aplurality of mappings between a first data set associated with the rawfeedback data and a second data set associated with a standardized,platform feedback data. The server system may use the plurality ofmappings to generate platform feedback data based on raw feedback data,and the resulting platform feedback data may be stored in one or moreformats configured for retrieval by one or more downstream subsystemsassociated with the server system.

While the exemplary system architecture as described in the presentdisclosure relates to electronic transactions for subscribing to,purchasing, or renting wearable items (e.g., clothing-as-a-service(CaaS) or Try-Then-Buy (TTB) service), implementations disclosed hereinmay effectively serve various other online transactions in the contextof any other subscription, purchase, rental, or retail services withoutdeparting from the scope of the disclosure, such as, for example,subscribing to or making purchases in a software service, cleaningservice, delivery service, maintenance service, rental product, rentalvehicles, etc. In addition, while some descriptions and examplesdisclosed in the present disclosure refer to certain exemplarytransactions as transactions pertaining to “apparel” or “garments,” allof those transactions may effectively serve any wearable item (e.g., anarticle of clothing, apparel, jewelry, hat, accessories, or any otherproduct which may be worn), or even hospitality linens, consumer goods,or any other textile fabrics, without departing from the scope of thedisclosure.

As used in the present disclosure, the term “CaaS” (i.e.,clothing-as-a-service) may collectively refer to computer-implementedservices and functions associated with subscription, purchase, and/orrental services for users (e.g., periodic subscription for receivingwearable items, apparel rental or purchase order, distribution, returnprocessing, TTB services, account management, marketing, customerservice, warehouse operations, etc.). As used in the present disclosure,the term “wearable item” may refer to any article of clothing, apparel,jewelry, hat, accessories, or other product which may be worn by aperson, an animal, or a thing, or be used as an ornament for a person,an animal, or a thing. As used herein, the term “closeting” or “tocloset” may refer to a computer-implemented operation of placing one ormore garments into a virtual closet (e.g., a cart, a repository, or anytype of space which may be virtually associated with a particular set ofone or more garments for a future transaction). Further, as used in thepresent disclosure, the term “wearability” may refer to a propensity ora probability of one or more users actually wearing a given garment, andthe term “wearability metric” may be a metric indicating a level ofwearability.

In accordance with the present disclosure, user interfaces, databases,periodically executed data exchange tasks run by subsystems of a serversystem, and automations being integrated together in a connectedplatform may be achieved by a uniquely configured system architecture,job execution clusters or components configuring one or more processorsto perform both storefront and back office tasks, and various userinterfaces providing specialized or customized access to users ofdifferent roles. For example, the system may periodically and/ordynamically obtain data attributes of each user's relationship withcertain apparel (e.g., a binary flag of whether a shipped garment wasactually worn by a user) by receiving and generating various forms ofuser feedback data, and train a neural network with those data sets tomake specific front-end user recommendations with highly wearableapparel. The ordered combination of various ad hoc and automated tasksin the presently disclosed platform necessarily achieve technologicalimprovements through the specific processes described more in detailbelow. In addition, the unconventional and unique aspects of thesespecific automation processes represent a sharp contrast to merelyproviding a well-known or routine environment for performing a manual ormental task.

The subject matter of the present description will now be described morefully hereinafter with reference to the accompanying drawings, whichform a part thereof, and which show, by way of illustration, specificexemplary embodiments. An embodiment or implementation described hereinas “exemplary” is not to be construed as preferred or advantageous, forexample, over other embodiments or implementations; rather, it isintended to reflect or indicate that the embodiment(s) is/are “example”embodiment(s). Subject matter can be embodied in a variety of differentforms and, therefore, covered or claimed subject matter is intended tobe construed as not being limited to any exemplary embodiments set forthherein; exemplary embodiments are provided merely to be illustrative.Likewise, a reasonably broad scope for claimed or covered subject matteris intended. Among other things, for example, subject matter may beembodied as methods, devices, components, or systems. Accordingly,embodiments may, for example, take the form of hardware, software,firmware, or any combination thereof (other than software per se). Thefollowing detailed description is, therefore, not intended to be takenin a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in one embodiment” as used herein does notnecessarily refer to the same embodiment and the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment. It is intended, for example, that claimed subject matterinclude combinations of exemplary embodiments in whole or in part.

The terminology used below may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized below; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection. Both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the features, as claimed.

In this disclosure, the term “based on” means “based at least in parton.” The singular forms “a,” “an,” and “the” include plural referentsunless the context dictates otherwise. The term “exemplary” is used inthe sense of “example” rather than “ideal.” The term “or” is meant to beinclusive and means either, any, several, or all of the listed items.The terms “comprises,” “comprising,” “includes,” “including,” or othervariations thereof, are intended to cover a non-exclusive inclusion suchthat a process, method, or product that comprises a list of elementsdoes not necessarily include only those elements, but may include otherelements not expressly listed or inherent to such a process, method,article, or apparatus. Relative terms, such as, “substantially” and“generally,” are used to indicate a possible variation of ±10% of astated or understood value.

Referring now to the appended drawings, FIG. 1 shows an exampleenvironment 100, according to one or more embodiments of the presentdisclosure. As shown, the example environment 100 may include one ormore networks 101 that interconnect a server system 102, user devices112, employee devices 116, tenant devices 120, and external systems 122.The one or more networks 101 may be, for example, one or more of acellular network, a public land mobile network, a local area network, awide area network, a metropolitan area network, a telephone network, aprivate network, an ad hoc network, an intranet, the Internet, a fiberoptic based network, a cloud computing network, etc. User devices 112may be accessed by users 108, employee devices 116 may be accessed byauthorized employees 114, and tenant devices 120 may be accessed byemployees of tenant entities 118. In some implementations, employeedevices 116 may be used to perform the functions of the tenant devices120 and/or the user devices 112. Server system 102 may comprise one ormore servers 104 and one or more databases 106, which may be configuredto store and/or process a plurality of data, microservices, and servicecomponents, and/or associated functions thereof, as described in moredetail below with respect to FIGS. 2 and 3.

Users 108 may access the server system 102 through the one or morenetworks 101 using user devices 112. Each device among the user devices112 may be any type of computing device (e.g., personal computingdevice, mobile computing devices, etc.) which allows users 108 todisplay a web browser or a web-based application for accessing theserver system 102 through the network 101. The user devices 112 may, forexample, be configured to display a web browser, a web-basedapplication, or any other user interface for allowing users 108 toexchange information with other device(s) or system(s) in theenvironment 100 over the one or more networks 101. For example, a deviceamong the user devices 110 may load an application with a graphical userinterface (GUI), and the application may display on the GUI one or moreapparel recommendations for closeting by the user. Users 108 accessinguser devices 112 may be, for example, users and/or potential users ofapparel made available for subscription-based distribution viaelectronic transactions and physical shipment. Additionally, oralternatively, users 108 may access user devices 112 to, for example,manage one or more user accounts, view catalogs, configure one or moreuser profiles, engage in customer service communications, make purchaseorders, track shipments, generate shipments, monitor order fulfillmentprocesses, initiate or process returns, order apparel for purchase,provide feedback, refer other users, navigate through various featuressuch as size advisor, perform personalized discovery, and/or makerecommendations.

Employee devices 116 may be configured to be accessed by one or moreemployees 114, including, for example, customer service employees,marketer employees, warehouse employees, analytics employees, or anyother employees who are authorized and/or authenticated to performtasks, operations, and/or transactions associated with the server system102, and/or the external systems 122. In one embodiment, employeedevices 116 are owned and operated by the same entity or at least anaffiliate of the entity operating the e-commerce (e.g., CaaS) businesshosted on server systems 102. Each device among the employee devices 116may be any type of computing device (e.g., personal computing device,mobile computing devices, etc.). The employee devices 116 may allowemployees 114 to display a web browser or an application for accessingthe server system 102 and/or the external systems 122, through the oneor more networks 101. For example, a device among the one or more of theemployee devices 116 may load an application with graphical userinterface (GUI), and the application may display on the GUI one or morewarehouse operations associated with providing CaaS to users 108. Insome implementations, the employee devices 116 may communicate directlywith the server system 102 via communications link 117 bypassing publicnetworks 101. Additionally, or alternatively, the employee devices 116may communicate with the server system 102 via network 101 (e.g., accessby web browsers or web-based applications).

Tenant devices 120 may be configured to be accessed by one or moretenants 118. Each device among the tenant devices 120 may be any type ofcomputing device (e.g., personal computing device, mobile computingdevices, etc.). As used herein, each tenant, among one or more tenants118, may refer to an entity that allocates and/or supplies one or morespecific collections of apparel for the CaaS inventory. For example,each of the one or more tenants 118 may be a retailer, a designer, amanufacturer, a merchandizer, or a brand owner entity that supplies oneor more collections of wearable items to the CaaS inventory managedand/or accessed by the server system 102. Tenants 118 may use one ormore electronic tenant interfaces (e.g., a catalog content managementsystem associated with each tenant) to provide the server system 102with wearable item data that describe apparel or wearable items madeavailable for electronic transactions on server system 102. For example,one or more catalogs for each of the one or more tenants 118 may begenerated and/or updated at the server system 102 dynamically and/orperiodically. Tenant devices 120 may serve as access terminals for thetenants 118, for communicating with the electronic tenant interfacesand/or other subsystems hosted at the server system 102. The tenantdevices 120 may, for example, be configured to display a web browser, anapplication, or any other user interface for allowing tenants 118 toload the electronic tenant interfaces and/or exchange data with otherdevice(s) or system(s) in the environment 100 over the one or morenetworks 101.

External systems 122 may be, for example, one or more third party and/orauxiliary systems that integrate and/or communicate with the serversystem 102 in performing various CaaS tasks. External systems 122 may bein communication with other device(s) or system(s) in the environment100 over the one or more networks 101. For example, external systems 122may communicate with the server system 102 via API (applicationprogramming interface) access over the one or more networks 101, andalso communicate with the employee devices 116 via web browser accessover the one or more networks 101.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples that differ from the example environment 100 of FIG. 1 arecontemplated within the scope of the present embodiments. In addition,the number and arrangement of devices and networks shown in system 100are provided as an example. In practice, there may be additionaldevices, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in system 100. Furthermore, two or more devices shown in FIG. 1may be implemented within a single device, or a single device shown inFIG. 1 may be implemented as multiple, distributed devices.Additionally, or alternatively, one or more devices may perform one ormore functions of other devices in the example environment 100. Forexample, employee devices 116 may be configured to perform one or morefunctions of tenant devices 120, in addition to their own functions.

FIG. 2 depicts a schematic diagram showing an exemplary process 200 forreceiving raw feedback data from a first type of user device andderiving platform feedback data at an integrated computing environment,according to one or more embodiments. The first type of user device mayinclude, for example, a mobile computing device configured to executeapplications, such as a smartphone, a tablet computing device, anycomputing device running a mobile operating system, or the like.Additionally, the first type of user device may also include a device ofany other type that is configured to access web-based user interfacesand/or communicate with one or more networks, such as personal computingdevice or a client terminal device of any computing environment.

The exemplary process 200 may be executed in an integrated computingenvironment. The integrated computing environment may include and/orinterconnect various components, such as user device(s) 222, controller224, parser 225, metrics mapper component 226, forms management system228, analytics engine 230, feedback service component 232, feedbackdatabase 234, and return notification service component 236. Thesecomponents 222-236 may be, for example, a set of computer-readableinstructions that configure one or more processors of the server system102, or a system among the external systems 122, to perform thefunctions of the exemplary process 200. Additionally, or alternatively,each of the components 222-236 may be an executable microservice (e.g.,modular system) being executed in the server system 102 using thecomputing resources of the server system 102, and/or an executableservice component in external systems 122 that configures one or moreprocessors in the environment 100 to perform the functions of theexemplary process 200. For example, the controller 224 may be anexecutable microservice among microservices in communication with theserver system 102, and the forms management system 228 may be anexecutable service component among the external systems 122 in theenvironment 100 depicted in FIG. 1.

At step 201, the controller 224 may receive a request for a returnnotification form identifier, from a user device 222. Such a request maybe initiated when the user device 222 and/or the controller 224 detectsa return notification trigger. In some implementations, a user device222 may correspond to a device among the user devices 112, and a user ofthe user device 222 may correspond to a user among the users 108. Thereturn notification trigger may be an incoming communication and/or aninput data at the user device 222 and/or the controller 224 thatindicates, for example, a selection to return one or more items that theuser purchased, rented, or received via a CaaS transaction. Theselection to return one or more items may include, for example, aselection entered by the user at a user interface to return one or moreitems, a selection entered by a user at a user interface to generate ashipping label for a return transaction, or a detection of an automatedor scheduled task for returning a previously transacted wearable item inaccordance with one or more preconfigured settings. Additionally, oralternatively, the return notification trigger may be, for example, anincoming communication and/or an input at the user device 222 and/or thecontroller 224 that indicates that the user at the user device 222 madea selection to cancel an ongoing CaaS transaction at any stage of thetransaction.

After receiving the request for a return notification form, thecontroller 224 may determine a return notification form identifier forthe user who made the request. In order to determine the returnnotification form as accurately as possible, the controller 224 mayfirst identify a segment associated with the return notification trigger(e.g., a segment associated with the wearable item(s) being returned,the wearable item(s) being cancelled, or the user providing the returnnotification). Each segment may be mapped to a specific returnnotification form identifier. If a return notification trigger isassociated with more than one segments (e.g., a segment corresponding toa first SKU (stock keeping unit) being returned, a segment correspondingto a second SKU being returned, and a segment corresponding to acharacteristic of the user), then the segments may be prioritized basedon one or more predetermined priority rules. A mapping of each segmentto its corresponding return notification form identifier may be storedin databases of metrics mapper component 226 and/or analytics engine230. An example of such mappings is shown in Table 1 below.

TABLE 1 Segment Return Notification Priority Segment Type FormIdentifier 1 premium_brands SKU f1 2 brand_xyz SKU f2 3segment_high_closeters User f3

At step 202, the controller 224 may send a request to the metrics mappercomponent 226, to determine the return notification form identifierusing the mapping of each segment to its corresponding returnnotification form identifier (e.g., Table 1 shown above). In someimplementations, the request to the metrics mapper component 226 may bea query being sent with input parameters, the input parameters includingsegment data associated with the return notification trigger. After oneor more look-up operations (e.g., a database query based on the segmentdata) at, for example, the mappings of each segment to its correspondingreturn notification form identifier, the controller 224 may determine,at step 203, the return notification form identifier via communicatingthe resulting identifier with the metrics mapper component 226. At step204, the controller 224 may transmit the determined return notificationform identifier to user device 222 as a response to the request made bythe user device in step 201.

At step 205, the user device 222 may communicate with forms managementsystem 228 to initiate a return notification feedback input processbased on the return notification form identifier obtained from thecontroller 224. At step 206, the forms management system 228 maycommunicate with the user device 222 to load an electronic returnnotification form associated with the return notification formidentifier, at a user interface of the user device 222. In someimplementations, the forms management system 228 may retrieve anexisting return notification form, by querying one or more databases(e.g., one or more databases among databases 106 or databases inexternal systems 122) using the return notification form identifier as aparameter. In some implementations, the forms management system 228 maybe an executable service component among the external systems 122,communicating with the user device 222 and the controller 224.

In some implementations, during the process of loading a returnnotification form, the forms management system 228 and/or the userdevice 222 may collect data indicative of a container information (e.g.,information about a container associated with a particular deviceplatform) of the user device 222, in order to generate a returnnotification form that is specific to the container corresponding to theuser device 222. For example, the forms management system 228 and/or theuser device 222 may include a form configuration data file that providesdefault return notification form identifier for a particular container(e.g., for a container specific to a particular mobile operating system,or a container specific to use of web browsers). The forms managementsystem 228 and/or the user device 222 may additionally include an SDK(Software Development Kit) that is configured to render the appropriatereturn notification form on the user interface of the user device 222 byselecting a return notification form at run time from the formconfiguration data file. For each container (e.g., among the containerscorresponding to various device platforms), there may be an SDKintegrated therewith, in order to be able to render the most compatiblereturn notification form on the user interface of the user device 222.

In some implementations, the forms management system 228 may generatethe return notification form to be loaded at the user device 222, byusing forms management data sets stored in one or more forms managementdatabases (e.g., one or more databases among databases 106). An exampleof the forms management data sets is shown in Table 2 below.

TABLE 2 Data set Data included in the data set Question pool List of aplurality of questions, each question including a unique questionidentifier Question config List of questions in the required returnnotification form A map that matches each return notification form withthe question identifiers belonging to the form Form identifier map A mapof form names to return notification form identifiers

The communications between user device 222 and the forms managementsystem 228 (e.g., steps 205 and 206) may also include receiving rawfeedback data from a user (e.g. a user among the users 108) of the userdevice 222 using the loaded return notification form. As used herein,raw feedback data may refer to the feedback data entered by the user atthe user device 222 based on the return notification form loaded at theuser device 222. In some implementations, receiving of the raw feedbackdata at the return notification feedback form may be performed in aniframe (inline frame) loaded at the user device 222. After the user ofthe user device 222 enters raw feedback data corresponding to the loadedreturn notification form, the raw feedback data may be transmitted, atstep 207, to the forms management system 228 and/or the controller 224for further processing. In some implementations, the user device 222 maytransmit the raw feedback data only to the forms management system 228,and the forms management system 228 may then transmit the raw feedbackdata to the controller 224 as an immediate response, a scheduled task,or a response to a data pull from controller 224.

After the controller 224 receives the raw feedback data, the controller224 may then parse the raw feedback data at the parser 225. The parser225 may be a subcomponent of the controller 224, or alternatively, theparser 225 may be a component in communication with the controller 224.In some implementations, the parser 225 may parse the raw feedback datainto one or more attributes, and request the metrics mapper component226, at step 208, to use a plurality of mappings stored in metricsmapper component 226 and/or the analytics engine 230 in order to derivethe platform feedback data from the attributes of the raw feedback data.The plurality of mappings may include one or more predefined mappingsbetween a first data set associated with the raw feedback data and asecond data set associated with the platform feedback data.Alternatively, the parser 225 may send the request to the metrics mappercomponent 226 without having to parse data attributes from the rawfeedback data.

In order to generate and/or maintain the plurality of mappings thataccurately map the raw feedback data to corresponding platform feedbackdata, the metrics mapper component 226 and/or the analytics engine 230may be in communication with one or more databases that include baselinedata sets serving as the data source for the mappings. Examples of suchbaseline datasets are shown in Table 3 below.

TABLE 3 Baseline data sets Data included in the data sets ReturnNotification Form Each form version mapped to a set of questionsQuestion Map (for raw Each question corresponding to unique questionidentifier feedback data) Each question identifier must be unique acrossall forms Return Notification Form Each form version mapped to a set ofanswers Answer Map (for raw Each answer corresponding to unique answeridentifier feedback data) Each answer identifier may be unique acrossall forms Platform Question Map (for A list of both unique and immutablequestions platform feedback data) Each question corresponding to aunique identifier Platform Answer Map (for A list of unique andimmutable answers platform feedback data) Each answer will have a uniqueidentifier Platform dimension Map (for Each question may be a dimensionplatform feedback data) Each dimension may have a set of unique valuesEach value may have a unique identifier Platform form map (for Each formin the platform corresponding to a unique platform feedback data) formversion Each form version may have a unique identifier

Based on the baseline data sets, the metrics mapper component 226 and/orthe analytics engine 230 may generate and/or maintain the plurality ofmappings. As a result, the plurality of mappings may include, forexample, at least a first map that matches each return notification formidentifier to a platform form identifier, a second map that matches eachreturn notification form question identifier to a platform questionidentifier, and a third map that matches each return notification formanswer identifier to a platform answer identifier. The first, second,and third maps may be preconfigured such that, the first map includesevery return notification form identifier (e.g., with each versionhaving its own identifier) being mapped to a corresponding platformform, while the second and third maps dynamically update to accuratelyreflect these mappings. In these maps, the return notification formidentifier, the return notification form question identifier, and thereturn notification form answer identifier may be updated as needed,because the return notification forms rendered for users at userdevice(s) 222 may vary depending on circumstances (e.g., user segment,brand of wearable item, vendor preference, version of the mobileapplication being executed on the user device 222, etc.). On the otherhand, platform form identifiers, platform question identifiers, andplatform answer identifiers may be immutable, because they may beutilized as a uniform set of core metrics that may be retrieved by othersubsystems of the environment 100.

At step 209, the metrics mapper component 226 may transmit the derivedplatform feedback data to the controller 224, in response to the requestmade at the step 208. In some implementations, the metrics mappercomponent 226 may include an application programming interface (API) tometrics mapper data, while the metrics mapper data (e.g., the maps andthe baseline data sets discussed above) may be data stored in databases(e.g., databases 106, or databases in metrics mapper component 226and/or analytics engine 230) that are in communication with the metricsmapper component 226. Under these implementations, the metrics mappercomponent 226 may be configured to, for example, receive a returnidentification form identifier and some raw feedback data, andcommunicate with the metrics mapper data via the API in order togenerate mapped data such as raw question identifier, raw question text,raw answer identifier, aw answer text, platform dimension values, etc.An example of mapped data in which raw feedback data has been mapped toplatform feedback data by the metrics mapper component 226 is shown inTable 4 below.

TABLE 4 Raw Raw Raw Raw Raw Platform Platform Form Question QuestionAnswer Answer Dimension Dimension ID ID Text ID Text Key Value f1 f1.q1Did you wear it? f1.q1.al “Yes” 1 Wear f1 f1.q1 Did you wear it?f1.q1.a2 “No” 2 Did not wear f1 f1.q1 Did you wear it? f1.q1.a2 “Justtried it on” 2 Did not wear f1 f1.q2 How did it fit? f1.q2.a1 “Great!” 1Great fit f1 f1.q2 How did it fit? f1.q2.a2 “Good!” 2 Okay fit f1 f1.q2How did it fit? f1.q2.a2 “Okay!” 2 Okay fit

At step 210, the parser 225 in communication with the controller 224 mayparse the attributes of the received platform feedback data, so that theattributes may be transmitted to feedback service component 232, and bestored at the feedback database 234. Alternatively, at step 210, thecontroller 224 may transmit the received platform feedback data tofeedback service component 232 without having to parse or separatedifferent attributes of the platform feedback data. At step 211, thefeedback service component may also transmit responses back tocontroller 224, such as, for example, an acknowledgement of receipt. Insome implementations, the platform feedback data may be stored atfeedback database 234 under BLOB (binary large object) data type.

Additionally, the feedback database 234 may be in communication with theanalytics engine 230, and may be configured to provide the platformfeedback data to analytics engine 230. This communication may,advantageously, enable the platform feedback data to be available forretrieval from various downstream subsystems of the server system 102.In some implementations, the platform feedback data may be stored inanalytics engine 230 in one or more formats configured for retrieval byother subsystems of the server system 102. For example, by being storedat the analytics engine 230, the platform feedback data may be used ashistorical data attributes for generating wearability metricscorresponding to, for example, each pair of a user and a SKU possiblefor CaaS transactions. Various embodiments of determining wearabilitymetrics of wearable items are disclosed, for example, in U.S. patentapplication Ser. No. 16/275,989, filed Feb. 14, 2019, entitled “Systemsand Methods for Automatic Apparel Wearability Model Training andPrediction,” which is incorporated herein by reference in its entirety.As another example, the platform feedback data may be used as fitratings of the wearable items available for CaaS distribution. Forexample, as shown in Table 4 above, user feedback corresponding tofit-related questions such as “how did it fit?” may be received from auser, be converted to platform feedback data (e.g., platform dimensionvalue) in accordance with mappings in metrics mapper component 226and/or analytics engine 230, and generate fit ratings attributes abouteach SKU. The fit ratings attributes may be used, for example, asparameters in automated personalized garment recommendations and/orvirtual closet assistant functions to CaaS users. In addition, theplatform feedback data may be used as one or more merchandise demandmetrics for SKUs, and the one or more merchandise demand metrics may beused by merchandising subsystems in planning inventory assortment (e.g.,budget, quantity, etc.) for future cycles.

At step 212, the controller 224 may also transmit the received platformfeedback data to return notification service component 236, and receivea response back at step 213 (e.g., acknowledgement of receipt, follow-upinquiry, etc.). The return notification service component 236 maymaintain, or communicate with, databases storing the received platformfeedback data, in order to keep track of the return notificationsreceived from the users. In some implementations, the platform feedbackdata may be stored in these databases in one or more formats configuredfor retrieval by other subsystems of the server system 102. The returnnotification service component 236 may also, for example, provide theplatform feedback data to a replenishment system of the server system102, as attributes associated with user's return notification. Theseattributes may be used by the replenishment system as a trigger togenerate replenishment identifiers (e.g., an identifier generated inresponse to a subscriber's return notification, for preparing orrecommending next shipment to the subscriber).

FIG. 3 depicts a schematic diagram showing an exemplary process 300 forreceiving raw feedback data from a second type of user device andderiving platform feedback data at an integrated computing environment,according to one or more embodiments. The second type of user device mayinclude, for example, a computing device configured to execute one ormore web browsers for communicating with one or more networks.Additionally, the second type of user device may also include a deviceof any other type that is configured to access web-based user interfacesand/or communicate with one or more networks.

At step 306A, the forms management system 328 may detect that a usercompleted data entry into a return notification feedback form, andsubsequently redirect a user at the user device 322 to a page thatinterfaces with the controller 324. The redirecting may be implemented,for example, by loading the return notification feedback form in aniframe loaded at the user device 322, and after completion of the formdata entry process, redirecting the user back to a page operated by thecontroller 324. In response to step 306A, a form API 323 of thecontroller 324 may interface with the forms management system 328 inorder to obtain the user's raw feedback data that was collected by theforms management system 328 via the electronic return notification form.Using the obtained raw feedback data, the controller 324 may, at step306B, transmit or load the raw feedback data onto a parent frame of theuser interface of the user device 322. Using the raw feedback datareceived at the user device 322 in step 306B, the user device 322 maythen proceed to transmit raw feedback data to the controller 324 forfurther processing.

Aside from steps 306A, 306B, and form API 323 described above, FIG. 3depicts elements (e.g., component and steps) that each correspond to anelement of FIG. 2. Between FIG. 2 and FIG. 3, corresponding elements arethose having matching reference numerals except for the hundredth digit.Thus, steps 301-305, steps 307-425, user device(s) 322, and components324-336 of the exemplary process 300 have been described in detailabove, with respect to the corresponding elements in the exemplaryprocess 200 of FIG. 2.

FIG. 4 depicts an exemplary method for deriving platform feedback datafrom raw feedback data for dynamic retrieval by downstream subsystems,according to one or more embodiments. The one or more processors of theserver system 102 may detect a return notification trigger of a user forone or more wearable items physically shipped to the user in response toone or more electronic transactions (step 405). In response to detectingthe return notification trigger, he one or more processors of the serversystem 102 may identify segment data associated with at least one of theuser and the one or more wearable items (step 410). Then, the one ormore processors of the server system 102 may determine a returnnotification form identifier based on the segment data, the returnnotification form identifier uniquely identifying an electronic form tobe filled out by the user (step 415). The one or more processors of theserver system 102 may load, at one or more user interfaces of a userdevice of the user, an electronic return notification form correspondingto the return notification form identifier (step 420). Subsequently, theone or more processors of the server system 102 may receive, via theelectronic return notification form, raw feedback data from the userdevice (step 425). The one or more processors of the server system 102may then derive platform feedback data from the raw feedback data usinga plurality of mappings stored in one or more electronic mappingdatabases, wherein the plurality of mappings include one or morepredefined mappings between a first data set associated with the rawfeedback data and a second data set associated with the platformfeedback data (step 430). After deriving the platform feedback data, theone or more processors of the server system 102 may store the platformfeedback data in at least one of a feedback service component and areturn notification service component, in one or more formats configuredfor retrieval by one or more downstream subsystems associated withmanaging and/or analyzing the one or more wearable items (step 435).

Although FIG. 4 shows example blocks of an exemplary method 400, in someimplementations, the exemplary method 400 may include additional blocks,fewer blocks, different blocks, or differently arranged blocks thanthose depicted in FIG. 4. Additionally, or alternatively, two or more ofthe blocks of the exemplary method 400 may be performed in parallel.

FIG. 5 depicts an exemplary computer device or system, in whichembodiments of the present disclosure, or portions thereof, may beimplemented. In some implementations, the server system 102, the userdevices 112, the employee devices 116, the tenant devices 120, the userdevice(s) 222, the controller 224, the forms management system 228, themetrics mapper component 226, the user device(s) 322, the controller324, the forms management system 328, the metrics mapper component 326,and/or any other computer system or user terminal for performing thevarious embodiments of the present disclosure, may correspond to device500. Additionally, each of the exemplary computer servers, databases,user interfaces, modules, and methods described above with respect toFIGS. 1-4 can be implemented in device 500 using hardware, software,firmware, tangible computer readable media having instructions storedthereon, or a combination thereof and may be implemented in one or morecomputer systems or other processing systems. Hardware, software, or anycombination of such may implement each of the exemplary systems, userinterfaces, and methods described above with respect to FIGS. 1-4.

If programmable logic is used, such logic may execute on a commerciallyavailable processing platform or a special purpose device. One ofordinary skill in the art may appreciate that embodiments of thedisclosed subject matter can be practiced with various computer systemconfigurations, including multi-core multiprocessor systems,minicomputers, mainframe computers, computer linked or clustered withdistributed functions, as well as pervasive or miniature computers thatmay be embedded into virtually any device.

For instance, at least one processor device and a memory may be used toimplement the above-described embodiments. A processor device may be asingle processor, a plurality of processors, or combinations thereof.Processor devices may have one or more processor “cores.”

Various embodiments of the present disclosure, as described above in theexamples of FIGS. 1-4, may be implemented using a processor device 500.After reading this description, it will become apparent to a personskilled in the relevant art how to implement embodiments of the presentdisclosure using other computer systems and/or computer architectures.Although operations may be described as a sequential process, some ofthe operations may in fact be performed in parallel, concurrently,and/or in a distributed environment, and with program code storedlocally or remotely for access by single or multi-processor machines. Inaddition, in some embodiments the order of operations may be rearrangedwithout departing from the spirit of the disclosed subject matter.

As shown in FIG. 5, a device 500 used for performing the variousembodiments of the present disclosure (e.g., the server system 102, theuser devices 112, the employee devices 116, the tenant devices 120, theuser device(s) 222, the controller 224, the forms management system 228,the metrics mapper component 226, the user device(s) 322, the controller324, the forms management system 328, the metrics mapper component 326,and/or any other computer system or user terminal for performing thevarious embodiments of the present disclosure) may include a centralprocessing unit (CPU) 520. CPU 520 may be any type of processor deviceincluding, for example, any type of special purpose or a general-purposemicroprocessor device. As will be appreciated by persons skilled in therelevant art, CPU 520 also may be a single processor in amulti-core/multiprocessor system, such system operating alone, or in acluster of computing devices operating in a cluster or server farm. CPU520 may be connected to a data communication infrastructure 510, forexample, a bus, message queue, network, or multi-core message-passingscheme.

A device 500 (e.g., the server system 102, the user devices 112, theemployee devices 116, the tenant devices 120, the user device(s) 222,the controller 224, the forms management system 228, the metrics mappercomponent 226, the user device(s) 322, the controller 324, the formsmanagement system 328, the metrics mapper component 326, and/or anyother computer system or user terminal for performing the variousembodiments of the present disclosure) may also include a main memory540, for example, random access memory (RAM), and may also include asecondary memory 530. Secondary memory, e.g., a read-only memory (ROM),may be, for example, a hard disk drive or a removable storage drive.Such a removable storage drive may comprise, for example, a floppy diskdrive, a magnetic tape drive, an optical disk drive, a flash memory, orthe like. The removable storage drive in this example reads from and/orwrites to a removable storage unit in a well-known manner. The removablestorage unit may comprise a floppy disk, magnetic tape, optical disk,etc., which is read by and written to by the removable storage drive. Aswill be appreciated by persons skilled in the relevant art, such aremovable storage unit generally includes a computer usable storagemedium having stored therein computer software and/or data.

In alternative implementations, secondary memory 530 may include othersimilar means for allowing computer programs or other instructions to beloaded into device 500. Examples of such means may include a programcartridge and cartridge interface (such as that found in video gamedevices), a removable memory chip (such as an EPROM, or PROM) andassociated socket, and other removable storage units and interfaces,which allow software and data to be transferred from a removable storageunit to device 500.

A device 500 may also include a communications interface (“COM”) 560.Communications interface 560 allows software and data to be transferredbetween device 500 and external devices. Communications interface 560may include a modem, a network interface (such as an Ethernet card), acommunications port, a PCMCIA slot and card, or the like. Software anddata transferred via communications interface may be in the form ofsignals, which may be electronic, electromagnetic, optical, or othersignals capable of being received by communications interface 560. Thesesignals may be provided to communications interface 560 via acommunications path of device 500, which may be implemented using, forexample, wire or cable, fiber optics, a phone line, a cellular phonelink, an RF link or other communications channels.

The hardware elements, operating systems and programming languages ofsuch equipment are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. A device 500 alsomay include input and output ports 550 to connect with input and outputdevices such as keyboards, mice, touchscreens, monitors, displays, etc.Of course, the various server functions may be implemented in adistributed fashion on a number of similar platforms, to distribute theprocessing load. Alternatively, the servers may be implemented byappropriate programming of one computer hardware platform.

The systems, apparatuses, devices, and methods disclosed herein aredescribed in detail by way of examples and with reference to thefigures. The examples discussed herein are examples only and areprovided to assist in the explanation of the apparatuses, devices,systems, and methods described herein. None of the features orcomponents shown in the drawings or discussed below should be taken asmandatory for any specific implementation of any of these theapparatuses, devices, systems, or methods unless specifically designatedas mandatory. For ease of reading and clarity, certain components,modules, or methods may be described solely in connection with aspecific figure. In this disclosure, any identification of specifictechniques, arrangements, etc. are either related to a specific examplepresented or are merely a general description of such a technique,arrangement, etc. Identifications of specific details or examples arenot intended to be, and should not be, construed as mandatory orlimiting unless specifically designated as such. Any failure tospecifically describe a combination or sub-combination of componentsshould not be understood as an indication that any combination orsub-combination is not possible. It will be appreciated thatmodifications to disclosed and described examples, arrangements,configurations, components, elements, apparatuses, devices, systems,methods, etc. can be made and may be desired for a specific application.Also, for any methods described, regardless of whether the method isdescribed in conjunction with a flow diagram, it should be understoodthat unless otherwise specified or required by context, any explicit orimplicit ordering of steps performed in the execution of a method doesnot imply that those steps must be performed in the order presented butinstead may be performed in a different order or in parallel.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Like referencenumerals are generally intended to refer to the same or similarcomponents. Components and modules can be implemented in software,hardware, or a combination of software and hardware. The term “software”is used expansively to include not only executable code, for examplemachine-executable or machine-interpretable instructions, but also datastructures, data stores and computing instructions stored in anysuitable electronic format, including firmware, and embedded software.The terms “information” and “data” are used expansively and includes awide variety of electronic information, including executable code;content such as text, video data, and audio data, among others; andvarious codes or flags. The terms “information,” “data,” and “content”are sometimes used interchangeably when permitted by context.

It is intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the disclosure beingindicated by the following claims.

What is claimed is:
 1. A computer-implemented method for generatingplatform feedback data from raw feedback data for dynamic retrieval bydownstream subsystems of a subscription electronic transactionsplatform, the method comprising: detecting, by one or more processors, areturn notification trigger of a user for one or more wearable itemsphysically shipped to the user in response to one or more electronictransactions of the subscription electronic transactions platform; inresponse to detecting the return notification trigger, identifying, bythe one or more processors, segment data associated with at least one ofthe user and the one or more wearable items shipped to the user;determining, by the one or more processors, a return notification formidentifier based on the segment data, the return notification formidentifier uniquely identifying an electronic return notification formto be filled out by the user; transmitting the electronic returnnotification form corresponding to the return notification formidentifier for display at one or more user interfaces of a user deviceof the user; receiving, by the one or more processors, via theelectronic return notification form, raw feedback data from the userdevice relating to the one or more wearable items shipped to the user;converting, by the one or more processors, the raw feedback data intoplatform feedback data having a format that is standardized across thesubscription electronic transactions platform by parsing the rawfeedback data into one or more attributes and deriving the platformfeedback data having the format that is standardized across thesubscription electronic transactions platform based on the one or moreattributes using one or more predefined mappings between the rawfeedback data and the platform feedback data, the one or more predefinedmappings comprising (i) a first map that matches the return notificationform identifier to a platform form identifier, (ii) a second map thatmatches one or more return notification form question identifiers to oneor more platform question identifiers that are unique across a pluralityof return notification forms associated with a plurality of returnnotification form identifiers, and (iii) a third map that matches one ormore return notification form answer identifiers to one or more platformanswer identifiers that are unique across the plurality of returnnotification forms associated with a plurality of return notificationform identifiers; and storing, by the one or more processors, theplatform feedback data in at least one of a feedback service componentand a return notification service component, in one or more formatsconfigured for retrieval by one or more downstream subsystems associatedwith managing and/or analyzing the one or more wearable items across thesubscription electronic transactions platform.
 2. The method of claim 1,wherein the return notification trigger comprises at least one of: auser selection to return the one or more wearable items, a userselection to generate a shipping label, and a preconfigured automatedtrigger.
 3. The method of claim 1, wherein transmitting the electronicreturn notification form corresponding to the return notification formidentifier for display at one or more user interfaces of the user deviceof the user further comprises: generating, by the one or moreprocessors, the electronic return notification form, using one or moreforms management data sets stored in one or more forms managementdatabases.
 4. The method of claim 3, wherein the one or more formsmanagement data sets comprise: a question pool including a plurality ofquestion identifiers, and a question configuration data set including amap matching the return notification form identifier with a set ofquestion identifiers among the plurality of question identifiers.
 5. Themethod of claim 1, wherein transmitting the electronic returnnotification form corresponding to the return notification formidentifier for display at one or more user interfaces of the user deviceof the user further comprises: retrieving the electronic returnnotification form, by querying one or more databases using the returnnotification form identifier.
 6. The method of claim 1, whereinconverting the raw feedback data into platform feedback data having theformat that is standardized across the subscription electronictransactions platform using the one or more predefined mappings storedin the one or more electronic mapping databases further comprises:communicating with the one or more predefined mappings via anapplication programming interface.
 7. A computer system for generatingplatform feedback data from raw feedback data for dynamic retrieval bydownstream subsystems of a subscription electronic transactionsplatform, the computer system comprising: a memory havingprocessor-readable instructions stored therein; and at least oneprocessor configured to access the memory and execute theprocessor-readable instructions, which when executed by the at least oneprocessor configures the at least one processor to perform a pluralityof functions, including functions for: detecting a return notificationtrigger of a user for one or more wearable items physically shipped tothe user in response to one or more electronic transactions of thesubscription electronic transactions platform; in response to detectingthe return notification trigger, identifying segment data associatedwith at least one of the user and the one or more wearable items shippedto the user; determining a return notification form identifier based onthe segment data, the return notification form identifier uniquelyidentifying an electronic return notification form to be filled out bythe user; transmitting the electronic return notification formcorresponding to the return notification form identifier for display atone or more user interfaces of a user device of the user; receiving viathe electronic return notification form, raw feedback data from the userdevice relating to the one or more wearable items shipped to the user;converting the raw feedback data into platform feedback data having aformat that is standardized across the subscription electronictransactions platform by parsing the raw feedback data into one or moreattributes and deriving the platform feedback data having the formatthat is standardized across the subscription electronic transactionsplatform based on the one or more attributes using one or morepredefined mappings between the raw feedback data and the platformfeedback data, the one or more predefined mappings comprising (i) afirst map that matches the return notification form identifier to aplatform form identifier, (ii) a second map that matches one or morereturn notification form question identifiers to one or more platformquestion identifiers that are unique across a plurality of returnnotification forms associated with a plurality of return notificationform identifiers, and (iii) a third map that matches one or more returnnotification form answer identifiers to one or more platform answeridentifiers that are unique across the plurality of return notificationforms associated with a plurality of return notification formidentifiers; and storing the platform feedback data in at least one of afeedback service component and a return notification service component,in one or more formats configured for retrieval by one or moredownstream subsystems associated with managing and/or analyzing the oneor more wearable items across the subscription electronic transactionsplatform.
 8. The system of claim 7, wherein the return notificationtrigger comprises at least one of: a user selection to return the one ormore wearable items, a user selection to generate a shipping label, anda preconfigured automated trigger.
 9. The system of claim 7, whereintransmitting the electronic return notification form corresponding tothe return notification form identifier for display at one or more userinterfaces of the user device of the user further comprises: generatingthe electronic return notification form, using one or more formsmanagement data sets stored in one or more forms management databases.10. The system of claim 9, wherein the one or more forms management datasets comprise: a question pool including a plurality of questionidentifiers, and a question configuration data set including a mapmatching the return notification form identifier with a set of questionidentifiers among the plurality of question identifiers.
 11. The systemof claim 7, wherein transmitting the electronic return notification formcorresponding to the return notification form identifier for display atone or more user interfaces of the user device of the user furthercomprises: retrieving the electronic return notification form, byquerying one or more databases using the return notification formidentifier.
 12. The system of claim 7, wherein converting the rawfeedback data into platform feedback data having the format that isstandardized across the subscription electronic transactions platformusing the one or more predefined mappings stored in the one or moreelectronic mapping databases further comprises: communicating with theone or more predefined mappings via an application programminginterface.
 13. A non-transitory computer-readable medium containinginstructions for generating platform feedback data from raw feedbackdata for dynamic retrieval by downstream subsystems of a subscriptionelectronic transactions platform, the computer system comprising:detecting a return notification trigger of a user for one or morewearable items physically shipped to the user in response to one or moreelectronic transactions of the subscription electronic transactionsplatform; in response to detecting the return notification trigger,identifying segment data associated with at least one of the user andthe one or more wearable items shipped to the user; determining a returnnotification form identifier based on the segment data, the returnnotification form identifier uniquely identifying an electronic returnnotification form to be filled out by the user; transmitting theelectronic return notification form corresponding to the returnnotification form identifier for display at one or more user interfacesof a user device of the user; receiving via the electronic returnnotification form, raw feedback data from the user device relating tothe one or more wearable items shipped to the user; converting the rawfeedback data into platform feedback data having a format that isstandardized across the subscription electronic transactions platform byparsing the raw feedback data into one or more attributes and derivingthe platform feedback data having the format that is standardized acrossthe subscription electronic transactions platform based on the one ormore attributes using one or more predefined mappings between the rawfeedback data and the platform feedback data, the one or more predefinedmappings comprising (i) a first map that matches the return notificationform identifier to a platform form identifier, (ii) a second map thatmatches one or more return notification form question identifiers to oneor more platform question identifiers that are unique across a pluralityof return notification forms associated with a plurality of returnnotification form identifiers, and (iii) a third map that matches one ormore return notification form answer identifiers to one or more platformanswer identifiers that are unique across the plurality of returnnotification forms associated with a plurality of return notificationform identifiers; and storing the platform feedback data in at least oneof a feedback service component and a return notification servicecomponent, in one or more formats configured for retrieval by one ormore downstream subsystems associated with managing and/or analyzing theone or more wearable items across the subscription electronictransactions platform.
 14. The non-transitory computer-readable mediumof claim 13, wherein the return notification trigger comprises at leastone of: a user selection to return the one or more wearable items, auser selection to generate a shipping label, and a preconfiguredautomated trigger.
 15. The non-transitory computer-readable medium ofclaim 13, wherein transmitting the electronic return notification formcorresponding to the return notification form identifier for display atone or more user interfaces of the user device of the user furthercomprises: generating the electronic return notification form, using oneor more forms management data sets stored in one or more formsmanagement databases.
 16. The non-transitory computer-readable medium ofclaim 15, wherein the one or more forms management data sets comprise: aquestion pool including a plurality of question identifiers, and aquestion configuration data set including a map matching the returnnotification form identifier with a set of question identifiers amongthe plurality of question identifiers.
 17. The non-transitorycomputer-readable medium of claim 13, wherein transmitting theelectronic return notification form corresponding to the returnnotification form identifier for display at one or more user interfacesof the user device of the user further comprises: retrieving theelectronic return notification form, by querying one or more databasesusing the return notification form identifier.
 18. The method of claim1, wherein the first map includes a plurality of return notificationform identifiers that respectively correspond to a plurality of returnnotification form versions.
 19. The method of claim 18, furtherincluding dynamically updating the second map and the third map based onthe first map.
 20. The method of claim 19, further including varying theplurality of return notification form versions based on the segment dataassociated with the one or more wearable items shipped to the user.